Wearable device with user authentication interface

ABSTRACT

A wearable device is used to authenticate a user into a user account at a user device of the user. In particular, the wearable device may include a sensor configured to detect whether the wearable device is worn by or is with the user. If so, the wearable device may send a signal to the user device and the user device may authenticate the user based on the signal received from the wearable device. For example, when the sensor detects that the wearable device is worn by the user, the wearable device may send a unique signal periodically, such as every five seconds or every 10 seconds. Based on whether the unique signal from the wearable device is received, the user device may authenticate the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/527,458, filed Oct. 29, 2014, which is incorporated herein byreference in its entirety.

BACKGROUND Field of the Invention

The present invention generally relates to wearable devices, and moreparticularly, to systems and methods for implementing authentication viathe wearable devices.

Related Art

With the popularity of internet and online commerce, consumersincreasingly are using online services for various transactions andinteractions. For example, consumers may shop online, make electronicpayments, and/or communicate electronically via email services orinstant message services. Many of the online services require consumersto set up an account and login credentials. Consumers are then requiredto log in, such as entering a login ID and password, to be authenticatedbefore consumers may use the services. Thus, the authentication processmay be inconvenient for a consumer, especially when the consumer has aplurality of different service accounts that require differentauthentication credentials. Consequently, there is a need for an easierway to authenticate a consumer that is both secure and convenient.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a networked system suitable forimplementing wearable devices for user authentication according to anembodiment.

FIG. 2 is a block diagram of a wearable device suitable for implementinguser authentication according to one embodiment.

FIG. 3A is a diagram illustrating a perspective front view of a watchtype wearable device according to one embodiment.

FIG. 3B is a diagram illustrating a perspective rear view of the watchtype wearable device of FIG. 3A according to one embodiment.

FIG. 3C is a diagram illustrating a perspective view of a band typewearable device according to one embodiment.

FIG. 3D is a diagram illustrating a perspective view of a ring typewearable device according to one embodiment.

FIG. 3E is a diagram illustrating perspective view of a glasses typewearable device according to one embodiment.

FIG. 3F is a diagram illustrating perspective view of a belt typewearable device according to one embodiment.

FIG. 4 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 according to one embodiment.

FIG. 5 is a flow chart illustrating a set up process for implementinguser authentication via a wearable device according to one embodiment.

FIG. 6 is a flow chart illustrating a method for implementing userauthentication via a wearable device according to one embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

According to an embodiment, a wearable device is used to authenticate auser into a user account at a user device of the user. In particular,the wearable device may include a sensor, such as an optical sensor or apressure sensor, configured to detect whether the wearable device isworn by or is with the user. If so, the wearable device may send asignal, such as a short range wireless signal, Bluetooth Low Energy orthe like, to the user device and the user device may authenticate theuser based on the signal received from the wearable device.

In an embodiment, the wearable device may include a sensor configured todetect whether the wearable device is worn by the user. When the sensordetects that the wearable device is worn by the user, the wearabledevice may send a unique signal periodically, such as every five secondsor every 10 seconds. When the sensor detects that the wearable device istaken off or otherwise separated from the user, the wearable device maystop sending the unique signal. Based on whether the unique signal fromthe wearable device is received, the user device may authenticate theuser.

In an embodiment, the sensor of the wearable device may be provided atan inner surface of the wearable device facing the user when thewearable device is worn by the user. The sensor may be an optical sensorconfigured to detect ambient light level. When the wearable device isworn by the user, the optical sensor may be covered by a body part ofthe user and may not receive light. When the wearable device is takenoff from the user, the optical sensor may be exposed and may receivelight. As such, the optical sensor may detect whether the wearabledevice is worn by the user.

In an embodiment, the sensor of the wearable device may be an actuator,such as a button, which may be depressed when the wearable device isworn by the user and may be released when the wearable device is takenoff the user. In another embodiment, the sensor may be a temperaturesensor configured to detect a temperature. For example, the temperaturesensor may detect a body temperature of the user when the wearabledevice is worn by the user and may detect ambient temperature of theuser when the wearable device is taken off from the user. In stillanother embodiment, the sensor may be a proximity sensor configured todetect a presence of the user when the wearable device is worn by theuser. In yet another embodiment, the sensor may be a pressure sensor ortouch sensor configured to detect a pressure force or a touch from theuser when the wearable device is worn by the user. Other sensors, suchas a gyroscope, accelerometer, and the like, also may be used to detectan orientation and movement of the wearable device to determine whetherthe wearable device is worn by the user or has been taken off from theuser.

In an embodiment, a user may set up the wearable device to be used foruser authentication with the user device. The user may designate orassociate the wearable device for user authentication with certainaccounts of the user. In an embodiment, one wearable device may be usedfor user authentication of multiple different user accounts. In anotherembodiment, multiple wearable devices may be used in combination foruser authentication of a particular user account. As such, variouscombinations of wearable devices may be used for user authentication ofdifferent user accounts.

In an embodiment, the user device may automatically authenticate theuser for a user account without requiring the user to enter credentials,such as passwords or login IDs, when the user device receives the uniquesignal from the wearable device indicating that the wearable device isstill worn by the user. In another embodiment, the user device mayrequire a login credential for the initial login and may keep the userlogged in as long as the user device receives the unique signal from thewearable device indicating that the wearable device is still worn by theuser. The user device may log the user out of the account when the userdevice no longer receives the unique signal from the wearable deviceindicating that the wearable device is no longer worn by the user or isseparated from the user. In an embodiment, if the user is logged out andthe user device receives the unique signal from the wearable device, theuser device may still require the user to provide credentials forlogging in. The user device may keep the user logged in thereafter aslong as the user device continues to receive the unique wireless signalsfrom the wearable device.

In an embodiment, the wearable device may be a watch type deviceconfigured to provide time related information and be worn by the user.In another embodiment, the wearable device may be a jewelry type item,such as a ring, a necklace, a wrist band, and the like. In still anotherembodiment, the wearable device may be a belt, a neck tie, a tie pin, acollar stay, and any other wearable accessories. In still anotherembodiment, the wearable may be a clip or a tab configured to beattached to the user or other items carried by the user.

FIG. 1 is a block diagram of a networked system suitable forimplementing wearable devices for user authentication according to anembodiment. Networked system 100 may comprise or implement a pluralityof servers and/or software components that operate to perform variouspayment transactions or processes. Exemplary servers may include, forexample, stand-alone and enterprise-class servers operating a server OSsuch as a MICROSOFT® OS, a UNIX® OS, a LINUX® OS, or other suitableserver-based OS. It can be appreciated that the servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such servers may be combined orseparated for a given implementation and may be performed by a greaternumber or fewer number of servers. One or more servers may be operatedand/or maintained by the same or different entities.

System 100 may include a user device 110, a merchant server 140, and apayment provider server 170 in communication over a network 160. Awearable device 104 may be worn by user 105 and may communicate withuser device 110. Payment provider server 170 may be maintained by apayment service provider, such as PayPal, Inc. of San Jose, Calif. Auser 105, such as a sender or consumer, utilizes user device 110 toperform a transaction using payment provider server 170. User 105 mayutilize user device 110 to initiate a payment transaction, receive atransaction approval request, or reply to the request. Note thattransaction, as used herein, refers to any suitable action performedusing the user device, including payments, transfer of information,display of information, etc. For example, user 105 may utilize userdevice 110 to initiate a deposit into a savings account. Although onlyone merchant server is shown, a plurality of merchant servers may beutilized if the user is purchasing products or services from multiplemerchants.

In some embodiments, the user 105 may have a payment account at thepayment provider server 170. The payment account may allow user 105 topurchase and/or pay for various products or services at a merchant. Theuser 105 may be required to enter credentials for user authentication atthe user device 110 to access and use the payment account. The wearabledevice 104 may be associated with the payment account of the user 105and be used for user authentication. The wearable device 104 may emit awireless signal, such as Bluetooth signal, Bluetooth Low Energy (BLE)signal, or other Near-Field Communication (NFC) signal, to indicate thatthe wearable device 104 is worn by the user 105. The user device mayauthenticate the user 105 based on the signal emitted from the wearabledevice 104.

User device 110, merchant server 140, payment provider server 170, andwearable device 104 may each include one or more processors, memories,and other appropriate components for executing instructions such asprogram code and/or data stored on one or more computer readable mediumsto implement the various applications, data, and steps described herein.For example, such instructions may be stored in one or more computerreadable media such as memories or data storage devices internal and/orexternal to various components of system 100, and/or accessible overnetwork 160. Network 160 may be implemented as a single network or acombination of multiple networks. For example, in various embodiments,network 160 may include the Internet or one or more intranets, landlinenetworks, wireless networks, and/or other appropriate types of networks.

User device 110 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication over network160. For example, in one embodiment, user device 110 may be implementedas a personal computer (PC), a smart phone, laptop computer, a wearablecomputing device, and/or other types of computing devices capable oftransmitting and/or receiving data, such as an iPad™ from Apple™.

User device 110 may include one or more browser applications 115 whichmay be used, for example, to provide a convenient interface to permituser 105 to browse information available over network 160. For example,in one embodiment, browser application 115 may be implemented as a webbrowser configured to view information available over the Internet, suchas a user account for setting up a shopping list and/or merchant sitesfor viewing and purchasing products and services. User device 110 mayalso include one or more toolbar applications 120 which may be used, forexample, to provide client-side processing for performing desired tasksin response to operations selected by user 105. In one embodiment,toolbar application 120 may display a user interface in connection withbrowser application 115.

User device 110 may further include other applications 125 as may bedesired in particular embodiments to provide desired features to userdevice 110. For example, other applications 125 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 160, or othertypes of applications.

Applications 125 may also include email, texting, voice and IMapplications that allow user 105 to send and receive emails, calls, andtexts through network 160, as well as applications that enable the userto communicate, transfer information, make payments, and otherwiseutilize a smart wallet through the payment provider as discussed above.User device 110 includes one or more user identifiers 130 which may beimplemented, for example, as operating system registry entries, cookiesassociated with browser application 115, identifiers associated withhardware of user device 110, or other appropriate identifiers, such asused for payment/user/device authentication. In one embodiment, useridentifier 130 may be used by a payment service provider to associateuser 105 with a particular account maintained by the payment provider. Acommunications application 122, with associated interfaces, enables userdevice 110 to communicate within system 100.

User device 110 may include a short distance communication device, suchas a Bluetooth device or a Near-Field Communication (NFC) deviceconfigured to communicate with other devices located near the userdevice 110. The Bluetooth device may implement low energy Bluetooth(BLE) communication. For example, user device 110 may communicate withwearable device 104 via BLE or NFC communication to indicate whether thewearable device is worn by the user.

Merchant server 140 may be maintained, for example, by a merchant orseller offering various products and/or services. The merchant may havea physical point-of-sale (POS) store front. The merchant may be aparticipating merchant who has a merchant account with the paymentservice provider. Merchant server 140 may be used for POS or onlinepurchases and transactions. Generally, merchant server 140 may bemaintained by anyone or any entity that receives money, which includesservice providers as well as banks and retailers. Merchant server 140may include a database 145 identifying available products (includingdigital goods) and/or services (e.g., collectively referred to as items)which may be made available for viewing and purchase by user 105.Accordingly, merchant server 140 also may include a marketplaceapplication 150 which may be configured to serve information overnetwork 160 to browser 115 of user device 110. In one embodiment, user105 may interact with marketplace application 150 through browserapplications over network 160 in order to view various products, fooditems, or services identified in database 145.

Merchant server 140 also may include a checkout application 155 whichmay be configured to facilitate the purchase by user 105 of goods orservices online or at a physical POS or store front. Checkoutapplication 155 may be configured to accept payment information from oron behalf of user 105 through payment service provider server 170 overnetwork 160. For example, checkout application 155 may receive andprocess a payment confirmation from payment service provider server 170,as well as transmit transaction information to the payment provider andreceive information from the payment provider (e.g., a transaction ID).Checkout application 155 may be configured to receive payment via aplurality of payment methods including cash, credit cards, debit cards,checks, money orders, or the like.

Payment provider server 170 may be maintained, for example, by an onlinepayment service provider which may provide payment between user 105 andthe operator of merchant server 140. In this regard, payment providerserver 170 includes one or more payment applications 175 which may beconfigured to interact with user device 110 and/or merchant server 140over network 160 to facilitate the purchase of goods or services,communicate/display information, and send payments by user 105 of userdevice 110.

Payment provider server 170 also maintains a plurality of user accounts180, each of which may include account information 185 associated withconsumers, merchants, and funding sources, such as banks or credit cardcompanies. For example, account information 185 may include privatefinancial information of users of devices such as account numbers,passwords, device identifiers, user names, phone numbers, credit cardinformation, bank information, or other financial information which maybe used to facilitate online transactions by user 105. In an embodiment,the account information 185 also may include information about wearabledevices of the user 105 that are associated with the user account of theuser 105 and that may be used to provide user authentication foraccessing the user account. Advantageously, payment application 175 maybe configured to interact with merchant server 140 on behalf of user 105during a transaction with checkout application 155 to track and managepurchases made by users and which and when funding sources are used.

A transaction processing application 190, which may be part of paymentapplication 175 or separate, may be configured to receive informationfrom user device 110 and/or merchant server 140 for processing andstorage in a payment database 195. Transaction processing application190 may include one or more applications to process information fromuser 105 for processing an order and payment using various selectedfunding instruments, including for initial purchase and payment afterpurchase as described herein. As such, transaction processingapplication 190 may store details of an order from individual users,including funding source used, credit options available, etc. Paymentapplication 175 may be further configured to determine the existence ofand to manage accounts for user 105, as well as create new accounts ifnecessary.

FIG. 2 is a block diagram of a wearable device suitable for implementinguser authentication according to one embodiment. Wearable device 104 maybe a wearable item that may be worn by the user 105 or be attached tothe user 105 or other items carried by the user 105. As such, thewearable device 104 may be a personal item to the user 105 that is wornor carried by the user 105. The wearable device 105 may include a sensor210 configured to detect whether the wearable device 105 is currentlybeing worn by the user 105. In an embodiment, the sensor 210 may be anoptical sensor configured to detect light, such as ambient light. Theoptical sensor may be provided on a surface of the wearable device 104interfacing with the user 105, such that when the user 105 is wearingthe wearable device 104, the optical sensor is covered and is notexposed to light or is exposed to minimal light. In an embodiment, thesensor may be a mechanical actuator, such as a mechanical button thatcan be depressed. The mechanical actuator may be provided on a surfaceof the wearable device 105 facing the user 105, such that when the user105 is wearing the wearable device 105, the mechanical actuator isactuated or depressed, and when the wearable device 105 is separatedfrom the user 105, the mechanical actuator is not actuated or isreleased.

In still another embodiment, the sensor 210 is a connector provided at afastening portion of the wearable device. For example, the connector maybe provided on a wrist band of a watch type wearable device 104 todetect when the wrist band is unbuckled. The connector may include twoconnecting portions that are selectively connected and disconnectedbased on whether the fastening portion of the wearable device isconnected or not. Thus, the connector may detect that the watch typewearable device is unbuckled and taken off the user when the connectoris disconnected.

In yet another embodiment, the sensor 210 is a pressure sensor or touchsensor, such as a capacitive or resistive touch screen configured todetect a pressure or a touch from the user. The pressure sensor or thetouch sensor may be provided on a surface of the wearable device 104facing the user 105's body part when the wearable device is worn by theuser 105. Thus, the sensor may detect that the wearable device 104 isworn by the user 105 when the sensor 210 is continuously contacted ortouched by a body part of the user 105.

In an embodiment, the sensor 210 is a temperature sensor configured todetect a temperature. The temperature sensor may be provided on asurface of the wearable device 104. In particular, the temperaturesensor is configured to contact or come in close proximity to a bodypart of the user 105 and to detect a body temperature of the user whenthe wearable device 104 is worn by the user 105. When the wearabledevice 104 is taken off of the user 105 or is separated from the user105, the temperature sensor may detect a drop of temperature from theuser 105's body temperature to a lower temperature, such as an ambienttemperature. Thus, the temperature sensor may detect whether thewearable device 104 is worn by the user 105.

In an embodiment, the sensor 210 may be a gyroscope or an accelerometerconfigured to detect an orientation and movement of the wearable device104. In particular, whether the wearable device 104 is worn by the user105 may be determined based on the movement patterns or orientations ofthe wearable device 104. For example, if the wearable device 104experiences abnormal shock, such being dropped on the floor, theaccelerometer may detect this abnormal shock which may be used todetermine that the wearable device 104 is separated from the user 105.In another example, certain movement patterns may be established to beassociated with the wearable device 104 being taken off from the user105.

In some embodiments, the wearable device 104 may include one or more ofthe aforementioned types of sensors to detect whether the wearabledevice 104 is still worn by the user 105. Different combinations ofsensors may be used in coordination with each other to provide betterdetections. For example, the optical sensor, the temperature sensor, andthe accelerometer may be used together to provide more accuratedetection of when the wearable device 104 is worn by the user 105 andwhen the wearable device 104 is taken off from the user 105.

The wearable device 104 may include a communication device 230configured to communicate with other devices. The communication device230 may include a short range communication device, such as a Bluetoothor Bluetooth Low Energy (BLE) communication device, a Near-FieldCommunication (NFC) device, WiFi, or a combination thereof. In anembodiment, the communication device 230 may include a signal emitterconfigured to emit a wireless signal, without receiving communicationfrom others. The communication device 230 may be configured to emit aunique wireless signal including unique patterns and/or frequencies,without a signal receiver. As such, the wearable device 104 may remaincompact and low cost. In another embodiment, the communication device230 may be configured to include a signal transmitter and a signalreceiver to emit and receive communication signals. The signal range ofthe communication device 230 may be limited to a few feet, such thatnearby devices may detect and/or communicate wirelessly.

The wearable device 104 may include a controller 220 configured tomanage and control various operations of the wearable device 104. Thecontroller 220 may include a microprocessor, an integrated circuit, or acombination thereof. The controller 220 may be configured or programmedto receive signals from the sensors 210 and make determinations ordecisions regarding controlling the operations of other devices, such asa communication device 230 and/or the output device 240. For example,based on the signals received from the sensors, the controller 220 maydetermine whether the wearable device 104 is still worn by the user andmay control the communication device 230 to emit signals accordingly.

The wearable device 104 also may include an output device 240 configuredto communicate with user 105. For example, output device 240 may be anaudio signal emitter configured to emit audio signals to the user 105.In another example, output device 240 may be an LED component configuredto provide visual output. In still another example, output device 240may be a vibration device configured to vibrate to communicate with user105. In some embodiments, output device 240 may include one or moretypes of different output devices, such as a combination of an LEDcomponent and an audio signal emitter to provide different types ofoutputs to the user 105.

The wearable device 104 may be powered by a battery, which may be arechargeable battery. For example, the wearable device 104 may bepowered by solar battery or by kinetic energy, such as the movement ofuser 105. In another example, the wearable device 104 may be powered byreplaceable batteries.

FIG. 3A is a diagram illustrating a perspective front view of a watchtype wearable device 104 a according to one embodiment. The watch typewearable device 104 a may include a watch case 310 within which variouscomponents, such as sensors 210, controller 220, communication device230 and output device 240, are disposed. The watch case 310 may includea front surface configured to display time. The front surface may be aglass surface and may include a touch screen configured to receiveinputs from the user 105. The watch type wearable device 104 a also mayinclude fastening portions 312 configured to fasten the watch typewearable device 104 a to the user 105.

FIG. 3B is a diagram illustrating a perspective rear view of the watchtype wearable device 104 a of FIG. 3A according to one embodiment. Therear surface of the watch case 310 may include a sensor 210 b. When thewatch type wearable device 104 a is worn by the user 105 or fastened tothe user 105, the rear surface may contact the user 105, such as a wristof the user 105. The sensor 210 b provided on the rear surface also maycontact the user 105. The sensor 210 b may be one or more of a pressuresensor, a contact sensor, a temperature sensor, an actuator type sensor,and the like that is configured to detect the user 105 when the watchtype wearable device 104 a is worn by the user 105 and the sensor 210 bcomes into contact with the user 105.

The watch type wearable device 104 a may also include sensors 210 aprovided at the fastening portion 312 of the watch type wearable device104 a. The sensors 210 a may be a connector type sensor configured todetect connection and disconnection of the fastening portions' 312 whenthe watch type wearable device 104 a is selectively fastened to andtaken off from user 105. When the watch type wearable device 104 a isfastened to the user 105 as detected by sensors 210 a and/or 210 b, thewatch type wearable device 104 a may emit a signal indicating that thewearable device 104 a is still worn by the user 105.

FIG. 3C is a diagram illustrating a perspective view of a band typewearable device 104 b according to one embodiment. The band typewearable device 104 b may include a band body 320 within which variouscomponents, such as sensors 210, controller 220, communication device230 and output device 240, are disposed. The band body 320 may includean inner surface 322 configured to contact the user 105 when the bandtype wearable device 104 b is worn by the user 105.

The inner surface 322 of the band body 320 may include a sensor 210 c.When the band type wearable device 104 b is worn by the user 105 orfastened to the user 105, the inner surface 322 may contact the user105, such as a wrist of the user 105. The sensor 210 c provided on theinner surface 322 also may contact the user 105. The sensor 210 c may beone or more of a pressure sensor, a contact sensor, a temperaturesensor, an actuator type sensor, and the like that is configured todetect the user 105 when the band type wearable device 104 b is worn bythe user 105 and the sensor 210 c comes into contact with the user 105.The band type wearable device 104 b may be a functional wrist band or ajewelry piece, such as a wrist band, a neck collar, and the like.

FIG. 3D is a diagram illustrating a perspective view of a ring typewearable device 104 c according to one embodiment. The ring typewearable device 104 c may include a ring body 330 and a setting 332.Various components, such as sensors 210, controller 220, communicationdevice 230 and output device 240, may be disposed in the ring body 330and/or setting 332. A sensor 210 d may be provided at the setting 332.When the ring type wearable device 104 c is worn by the user 105, abottom surface or inner surface of the ring body 33 and setting 332 maycontact the user 105. The sensor 210 d provided on the inner surfacealso may contact the user 105. The sensor 210 d may be one or more of apressure sensor, a contact sensor, a temperature sensor, an actuatortype sensor, and the like that is configured to detect the user 105 whenthe ring type wearable device 104 c is worn by the user 105 and thesensor 210 d comes into contact with the user 105.

FIG. 3E is a diagram illustrating perspective view of a glasses typewearable device 15) 104 d according to one embodiment. The glasses typewearable device 104 d may include an eyeglass frame including templeportions 342 connected to lens frames 340 via hinges 346. The lensframes 340 include a bridge portion 344. Various components, such assensors 210, controller 220, communication device 230 and output device240, may be disposed in the glass frame. In an example, sensors 210 emay be provided on the bridge portion 344 to detect user contacts.Sensors 210 e also may be provided on inner surfaces of temple portions342 to detect user contacts. The sensor 210 e may be one or more of apressure sensor, a contact sensor, a temperature sensor, an actuatortype sensor, and the like that is configured to detect contact with theuser 105. In an embodiment, sensors 210 e may be tension sensorsprovided at the hinges 346 to detect tensions at the hinges 346 when theglasses type wearable device 104 d is worn by the user 105. Thus,various sensors may be provided to detect whether the glasses typewearable device 104 d is worn by the user 105.

FIG. 3F is a diagram illustrating perspective view of a belt typewearable device 104 e according to one embodiment. The belt typewearable device 104 e may include a belt buckle portion 350 and a beltportion 352. Various components, such as sensors 210, controller 220,communication device 230 and output device 240, may be disposed in beltbuckle portion 350. In an example, a sensor 210 f may be provided at thebelt buckle portion 350. The sensor 210 f may be one or more of apressure sensor, a contact sensor, a temperature sensor, an actuatortype sensor, and the like that is configured to detect contact with theuser 105.

Other types of wearable devices 104 that may be attached to or carriedby the user 105 also may be utilized. For example, the wearable device104 may be a clip configured to attach to the user 105 or items carriedby the user 105. In another example, the wearable device 104 may be atab that may be inserted or placed inside a bag or a wallet of the user105.

FIG. 5 is a flow chart illustrating a set up process 500 forimplementing user authentication via a wearable device according to oneembodiment. Initially, the 105 may put the wearable device 104 on andmay turn on, if needed, the wearable device 104. The wearable device 104may then detect, by one or more sensors 210, that the wearable device104 is being worn by the user 105. The controller 220 of the wearabledevice 104 may then control the communication device 230 to generate andemit unique wireless signals. The unique wireless signals may be emittedat a particular frequency or pattern associated with the wearable device104. For example, different types of wearable devices may have differentfrequencies or patterns. In another example, the unique signal mayinclude information representing a unique device ID of the wearabledevice 104. The signal may be emitted periodically, such as every 5seconds or every 10 seconds, as long as the wearable device 104 is wornby the user 105. The signal also may carry information related to thewearable device 104, such as type, name, ID, description, specification,and/or status (whether worn by the user) of the wearable device 104.

At step 502, the user device 110 may detect the unique signal emittedfrom the wearable device 104. For example, the user device 110 may becarried by the user 105 or the user 105 is currently using the userdevice 110. As such, the user device 110 may be located within thewireless broadcast range of the wearable device 104. At step 504, theuser device 110 may register or receive the signal. The user device 110may analyze the signal from the wearable device 104 and may determinethat the signal is from a wearable device for user authentication. Theuser device 110 may ask the user 105 whether the user 105 would like toregister the wireless signal for user authentication. If so, the user105 may be allowed to designate one or more user accounts which may usethe signal for user authentication. For example, the user may associatethe wireless signal with user 105's payment account at a payment serviceprovider. As such, the wireless signal may be used to authenticate userfor that payment account.

At step 506, the user device 110 may authenticate user 105 for thedesignated account. For example, the user device 110 may ask for theuser's login ID, password, finger-print scan, and the like. When theuser 105 is authenticated successfully, the user device 110 may thenassociate the signals from the wearable device 104 with the designatedaccounts at step 508. As such, the unique signals from the wearabledevice 104 may be used to authenticate the user for the designatedaccounts.

At step 510, the user device 110 may allow the user 105 to select orinput authentication settings for the designated accounts with regard tothe signals. In particular, the user 105 may customize theauthentication process for the designated accounts with regard towhether the unique signals are received by the user device 110, e.g.,whether the wearable device 104 is worn by the user 105. For example, ifthe user device 110 determines that the user 105 is wearing the wearabledevice 104 based on the signals received from the wearable device 104,the user device 104 may keep the user 105 logged in as long as the userdevice 110 continues to receive signals from the wearable deviceindicating that the user 105 is still wearing the wearable device. Theuser device 110 may log user 105 out after a predetermined amount oftime (which can be immediately) if the user device 110 no longerreceives the signals from the wearable device 104.

In an embodiment, if the user device 110 detects the signals from thewearable device 104 indicating that the user 105 is wearing the wearabledevice 104, the user device 110 may automatically authenticate the user105 or log the user 105 into the designated account without requiringcredentials, such as passwords or login IDs. In still anotherembodiment, if the user device 110 detects the signals from the wearabledevice 104 indicating that the user 105 is wearing the wearable device104, the user device 110 may require less credentials for authenticationor have less strict security requirements. The user 105 may select andcustomize how the wearable device 104 may provide different features ofuser authentication for different user accounts.

In an embodiment, the user device 110 may allow the user to designate acombination of different signals from different wearable devices for aparticular account. For example, automatic user authentication may beimplemented for a particular account when the user device 110 detectsthat the user 105 is wearing both a particular ring type wearable deviceand a particular watch type wearable device. In an embodiment, differentcombinations of wearable devices may be designated for differentauthentication requirements. For example, when the user 105 is wearing aparticular combination of three wearable devices, the authenticationrequirement may be less than when the user 105 is wearing two of thethree wearable devices.

In an embodiment, one wearable device 104 may be used to provideauthentication for multiple of user's accounts. For example, when theuser 105 is wearing a particular watch type wearable device 104 a, theuser device 110 may keep the user 105 logged in at the user 105's bankaccount and at the user 105's shopping account. In another embodiment,different types of wearable devices 104 may provide different levels ofauthentication requirement. For example, wearing a ring-type wearabledevice 104 c may allow automatic access to an account, while wearing awatch-type wearable device 104 a may still require the user 105 to enterhis/her user ID.

At step 512, the user device 110 may confirm set up with the user 105.For example, a notification may be provided on the user device 110 toinform the user 105 that a particular wearable device 104 is now set upfor user authentication of a particular user's account. In anotherexample, the output device 240 at the wearable device 104 may confirmthe set up by beeping, LED flashing or color change, vibrations, orinformation display (on a screen). The user device 110 may store andupdate the authentication settings of various accounts of the user 105and their respective associated wearable devices. The user device 110may provide a user interface for the user 105 to update, add, delete,and/or modify the authentication settings related to wearable devices.

FIG. 6 is a flow chart illustrating a method 600 for implementing userauthentication via a wearable device according to one embodiment. Atstep 602, the user device 110 may detect unique signals from a wearabledevice 104. For example, when the user 105 puts on the wearable device104, the wearable device 104 may detect the user 105 via sensors 210 andmay begin to emit the unique signals. In an embodiment, the wearabledevice 104 may previously have been registered with the user device 110,such that the wearable device 104 may automatically be paired with theuser device 110, e.g., via Bluetooth communication.

At step 604, the user device 110 may determine whether the uniquesignals are for user authentication. In particular, the user device 110may check and see if the received unique signals are associated with oneor more of the user 105's accounts. If so, the user device 110 also maylook up the authentication settings to determine how the unique signalsmay alter the authentication process for the account. At step 606, theuser device 110 may authenticate the user 105 based on theauthentication settings for the designated account in view of thedetected signals. For example, if the user 105 has not been logged intothe account, the user device 110 may log the user 105 in automaticallywithout requiring user credentials in view of the signals received fromthe wearable device 104. If the user 105 already is logged into theaccount, the user device 110 may maintain the logged in session in viewof the signals received from the wearable device 104.

At step 608, the user device 110 may determine whether the signals fromthe wearable device 104 are received continuously at the user device110. For example, the wearable device 104 may emit the signalsperiodically, e.g., every few seconds. The user device 110 may determinewhether the signals are received periodically from the wearable device104 indicating that the user 104 still is wearing the wearable device104. If the user device 110 continues to receive the signals from thewearable device 104, the user device 110 may keep the user 105authenticated at step 610. For example, the user device 110 may keep theuser 105 logged in at the account. In another example, the user device110 may have a lower security requirement or authentication requirementfor logging in when the user device 110 continuously receives thesignals from the wearable device 104. The process then may go back tostep 608 where the user device 110 continues to check whether thesignals from the wearable device 104 still are detected at the userdevice 110.

If the user device 110 stops receiving the signals from the wearabledevice 104 which indicates that the wearable device is taken off fromthe user 105 or is separated from the user 105, the user device 110 maylog user 105 out of the account or stop authenticating the user 105immediately or within a certain time period, which may depend on user,system, and/or account settings. In another example, the user device 110may require higher or stricter authentication requirements when the user105 is not wearing the wearable device 104.

After the wearable device 104 has been taken off from the user 105, theuser device 110 may require that the user 105 provide authenticationcredentials to log in again even if the wearable device 104 has been putback on the user 105. This may ensure that the wearable device 104 isnot worn by another user for the purpose of unauthorized access to theuser's account.

By implementing processes 500 and 600, a wearable device 104 may beprovided to facilitate easier and safer authentication process for theuser 105. In particular, the wearable device 104 may include sensorsthat may detect whether the wearable device 104 is worn or attached tothe user 105. The wearable device 104 may be configured to emit signalsindicating that the wearable device 104 is worn by the user 105. Basedon the status of the wearable device 104, the user device 110 may allowautomatic or easier authentication process for the user's account. Theautomatic or easier authentication may end once the wearable device 104is taken off from the user 105 to provide security to the user'saccount.

In the above embodiments, the wearable device 104 is utilized forauthentication into user's accounts at the user device 104. In anotherembodiment, the wearable device 104 may be utilized for userauthentication for access into buildings, areas, events, vehicles,transportation networks, and any location where user authentication isrequired.

FIG. 4 is a block diagram of a computer system 400 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, Bluetooth device, key FOB, badge, wearable computingdevice, etc.) capable of communicating with the network. The merchantand/or payment provider may utilize a network computing device (e.g., anetwork server) capable of communicating with the network. It should beappreciated that each of the devices utilized by users, merchants, andpayment providers may be implemented as computer system 400 in a manneras follows.

Computer system 400 includes a bus 402 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 400. Components include aninput/output (I/O) component 404 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 402. I/O component404 may also include an output component, such as a display 411 and acursor control 413 (such as a keyboard, keypad, mouse, etc.). Anoptional audio input/output component 405 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 405 may allow the user to hear audio. Atransceiver or network interface 406 transmits and receives signalsbetween computer system 400 and other devices, such as another userdevice, a merchant server, or a payment provider server via network 160.In one embodiment, the transmission is wireless, although othertransmission mediums and methods may also be suitable. A processor 412,which can be a micro-controller, digital signal processor (DSP), orother processing component, processes these various signals, such as fordisplay on computer system 400 or transmission to other devices via acommunication link 418. Processor 412 may also control transmission ofinformation, such as cookies or IP addresses, to other devices.

Components of computer system 400 also include a system memory component414 (e.g., RAM), a static storage component 416 (e.g., ROM), and/or adisk drive 417. Computer system 400 performs specific operations byprocessor 412 and other components by executing one or more sequences ofinstructions contained in system memory component 414. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 412 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 414, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 402. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 400. In various other embodiments of thepresent disclosure, a plurality of computer systems 400 coupled bycommunication link 418 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A system, comprising: a non-transitory memorycomprising instructions; and one or more hardware processors coupled tothe non-transitory memory and configured to read the instructions tocause the system to perform operations comprising: detecting, from auser device, a request for access to a first user account of a user;detecting, via the user device, a first signal received from a firstwearable device of the user when the first wearable device determinesthat it is being worn by the user; detecting, via the user device, asecond signal received from a second wearable device of the user whenthe second wearable device determines that it is being worn by the user;authenticating the user based on the first signal and the second signal;providing the user device with access to the first user account;monitoring the first signal and the second signal; and logging the userdevice out of the first user account after a period of time in responseto detecting the first signal or the second signal has ended based onthe monitoring.
 2. The system of claim 1, wherein the detecting thefirst signal is in response to the first wearable device determiningthat an actuator on the first wearable device has been depressed.
 3. Thesystem of claim 1, wherein the detecting the first signal is in responseto the first wearable device determining that a temperature sensorlocated on the first wearable device detects a temperature associatedwith the user.
 4. The system of claim 1, wherein the first signal isunique to the first wearable device.
 5. The system of claim 1, whereinthe first wearable device is configured to transmit the first signalperiodically when the first wearable device determines that it is beingworn by the user.
 6. The system of claim 1, wherein the first useraccount is associated with a first authentication level that isdifferent from a second authentication level associated with a seconduser account of the user.
 7. The system of claim 6, wherein the firstauthentication level includes detecting the first signal from thewearable device, and wherein the second authentication level includesdetecting the first signal from the first wearable device and the secondsignal from the second wearable device associated with the user.
 8. Anon-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine to performoperations comprising: detecting, from a user device, a request foraccess to a first user account of a user; detecting, via the userdevice, a first signal received from a first wearable device of the userwhen the first wearable device determines that it is being worn by theuser; and detecting, via the user device, a second signal received froma second wearable device of the user when the second wearable devicedetermines that it is being worn by the user; authenticating the userbased on the first signal and the second signal; providing the userdevice with access to the first user account; monitoring the firstsignal and the second signal; and logging the user device out of thefirst user account after a period of time in response to detecting thefirst signal or the second signal has ended based on the monitoring. 9.The non-transitory machine-readable medium of claim 8, wherein thedetecting the first signal is in response to the first wearable devicedetermining that-an actuator on the first wearable device has beendepressed.
 10. The non-transitory machine-readable medium of claim 8,wherein the detecting the first signal is in response to the firstwearable device determining that temperature sensor located on the firstwearable device detects a temperature associated with the user.
 11. Thenon-transitory machine-readable medium of claim 8, wherein the firstsignal is unique to the first wearable device.
 12. The non-transitorymachine-readable medium of claim 8, wherein the first wearable device isconfigured to transmit the first signal periodically when the firstwearable device determines that it is being worn by the user.
 13. Thenon-transitory machine-readable medium of claim 8, wherein the firstuser account is associated with a first authentication level that isdifferent from a second authentication level associated with a seconduser account of the user.
 14. A method, comprising: detecting, from auser device, a request for access to a first user account of a user;detecting, via the user device, a first signal received from a firstwearable device of the user when the first wearable device determinesthat it is being worn by the user; and detecting, via the user device, asecond signal received from a second wearable device of the user whenthe second wearable device determines that it is being worn by the user;authenticating the user based on the first signal and the second signal;providing the user device with access to the first user account;monitoring the first signal and the second signal; and logging the userdevice out of the first user account after a period of time in responseto detecting the first signal or the second signal has ended based onthe monitoring.
 15. The method of claim 14, wherein the wearable devicewherein the detecting the first signal is in response to the firstwearable device determining that actuator on the first wearable devicehas been depressed.
 16. The method of claim 14, wherein the detectingthe first signal is in response to the first wearable device determiningthat temperature sensor located on the first wearable device detects atemperature associated with the user.
 17. The method of claim 14,wherein the first signal is unique to the first wearable device.
 18. Themethod of claim 14, wherein the first wearable device is configured totransmit the first signal periodically when the first wearable devicedetermines that it is being worn by the user.
 19. The method of claim14, wherein the first user account is associated with a firstauthentication level that is different from a second authenticationlevel associated with a second user account of the user.
 20. The methodof claim 19, wherein the first authentication level includes detectingthe first signal from the first wearable device, and wherein the secondauthentication level includes detecting the first signal from thewearable device and the second signal from the second wearable deviceassociated with the user.